Todo

• Config defaults Mechanism to describe defaults in config yetibot#1017
• Support overriding any config using channel settings or user-specific settings
• Write the corresponding "Channel as context" guide
• Generate config from specs (instead of maintaining the 3 formats of sample configs at https://github.com/yetibot/yetibot.core/tree/master/config). Maybe a ClojureScript project that creates a React config component and publishes it to bit.dev
• Add config getter to cmd-hook. This couples together a schema, a command and its namespace, and a subset of configuration. If the config is not present/valid, when a user tries to execute the command, the command would then report an error that it is not configured and a link to the exact subset of configuration it requires. This also allows yetibot core to pass the requested config submap to command handler functions, which means core can optionally override it based on channel settings (
• Audit all the specs and try to narrow them down, e.g. yetibot.url should be a url that does not end with a / (alternatively, parse it with the uri lib and get the part we want).

Issues

• Fixes Allow whether sub expressions are enabled to be configured on a per-channel basis yetibot#982
• Fixes Allow default command to be configured on a per channel basis yetibot#870
• Maybe fixes Proposal: Dynamic ssh hosts config yetibot#965 (verify)
• Related: More general way to parameterize commands from the context of a channel yetibot#1005
• Related: Ability to enable/disable all observers on a channel specific basis yetibot#1007

Tools

• data-specs